MB - Sampling Period
--------------------

This transactions defines the times when the monitor was operating.

This transaction contains the start and end dates for one or more sampling periods for each monitor.

Periodic monitoring is indicated by having multiple sampling periods with gaps between them.  You may not have overlapping periods or more than one period with a null end date (indicating that sampling period is still open / ongoing).

Rules
^^^^^

The beginning of a sample period cannot be changed with an update (U) transaction.

To enter a Monitor record, you must also enter a Sampling Period record.

A sampling period cannot be deleted for a production monitor if that deletion would leave the monitor with no sample periods.

A sampling period record cannot be deleted if data for a monitor has been reported during the period.  

Data cannot be submitted for a monitor outside of a sampling period.

A sampling period cannot be changed (updated or deleted) in a manner that would exclude existing raw, blank, or QA data from that sample period.

Examples:

.. code-block:: text
   :caption: MB transaction in default mode

   MB|I|06|001|0007|88101|3|20110101|

.. code-block:: text
   :caption: MB transaction in Tribal mode

   MB|I|TT|614|7004|81102|1|20020701|



Format
^^^^^^

.. list-table:: MB - Sample Period transaction format
   :widths: 1 5 15 4 3 1
   :header-rows: 1


   * - Seq.
     - Name
     - Description
     - Formatting Rules
     - Required
     - Key
   * - 1
     - `Transaction Type <Transaction%20Type.html>`_
     - Monitor Sampling Period transaction identifier.
     - Must = MB
     - Always
     - 
   * - 2
     - `Action Indicator <Action%20Indicator%20for%20Transaction.html>`_
     - Indicator for Insert, Update, or Delete action.
     - Must = I, U, or D
     - Always
     - 
   * - 3
     - `State Code / Tribal Indicator <State%20Code.html>`_
     - The FIPS state code of the monitor, or "TT" to indicate that the next field on the transaction is a Tribal code.
     - Must exist in STATES Reference Table or be 'TT' for Tribal Site
     - Always
     - Y
   * - 4
     - `County Code / Tribal Code <County%20Code.html>`_
     - The FIPS County Code of the site.  If the previous field on the transaction contains "TT", then the Tribal Code of the site.
     - Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table
     - Always
     - Y
   * - 5
     - `Site Number <Site%20Number.html>`_
     - Four digit number to uniquely identify site in county and/or tribe.
     - Must exist in SITES table with {State Code, county Code} or Tribal Code
     - Always
     - Y
   * - 6
     - `Parameter Code <Parameter%20Code.html>`_
     - The AQS parameter code assigned to the monitor in AQS.
     - Must exist in PARAMETERS reference table.
     - Always
     - Y
   * - 7
     - `POC <POC.html>`_
     - Parameter Occurrence Code:  One or two digit number identifying a specific monitor for a parameter at the site.  
     - Must exist in MONITOR table for non-Insert actions.
     - Always
     - Y
   * - 8
     - `Sampling Period Begin Date <Sampling%20Period%20Begin%20Date.html>`_
     - The date on which a distinct period of operations began.
     - YYYYMMDD.
     - Always
     - Y
   * - 9
     - `Sampling Period End Date <Sampling%20Period%20End%20Date.html>`_
     - The date on which a distinct period of operations ended.
     - YYYYMMDD.
     - No
     -